From 7c941f9205572ccc7300a0c071c15ff04963de82 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Sat, 11 Jul 2026 22:44:32 +0000 Subject: [PATCH] Fix GPS -> UTM --- doc/src/tables/events.m4 | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/src/tables/events.m4 b/doc/src/tables/events.m4 index aab6cf2..3a6caf3 100644 --- a/doc/src/tables/events.m4 +++ b/doc/src/tables/events.m4 @@ -335,7 +335,7 @@ The following table lists these rules and implications: finished. -.. _EVENTS_gps_code: +.. _EVENTS_utm_code: ``sdb_utm`` (UTM Location) A record of an individual's location recorded in UTM @@ -365,10 +365,10 @@ The following table lists these rules and implications: The |ROLES| row related to the event, the row with a |ROLES|.\ |ROLES.EID| value equal to the EVENTS.\ |EVENTS.EID| value, designates the individual that was located. - There may be at most one |ROLES| row related to the GPS location + There may be at most one |ROLES| row related to the UTM location event. The system will generate a warning when there is no |ROLES| row - related to the GPS location event. + related to the UTM location event. The individual located must be the the focal of the follow, when the related |WATCHES| row represents a follow, and must be located @@ -376,7 +376,7 @@ The following table lists these rules and implications: spatial location. This means that the |ROLES| row related to the event must have a |ROLES|.\ |ROLES.Participant| value equal to the |WATCHES|.\ - |WATCHES.AnimID| of the |WATCHES| row related to the GPS location + |WATCHES.AnimID| of the |WATCHES| row related to the UTM location event. Both the EVENTS.\ |EVENTS.Start| and EVENTS.\ |EVENTS.Stop| @@ -400,7 +400,7 @@ The following table lists these rules and implications: of the location event, and the event has a related |ROLES| row where the |ROLES|.\ |ROLES.Participant| is the located individual. - For GPS location events, the EVENTS.\ |EVENTS.Certainty| column + For UTM location events, the EVENTS.\ |EVENTS.Certainty| column must be ``sdb_identity_certain``. -- 2.34.1